-
-
Notifications
You must be signed in to change notification settings - Fork 103
feat(2.9): deprecate ResetDatabase
trait
#985
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: 2.x
Are you sure you want to change the base?
feat(2.9): deprecate ResetDatabase
trait
#985
Conversation
ResetDatabase
trait
43f4a0b
to
91dd0a7
Compare
91dd0a7
to
a3f404b
Compare
1ec9784
to
4272d7d
Compare
8a6d6df
to
3721f01
Compare
f898cd3
to
f48fbd2
Compare
public function boot(): void | ||
{ | ||
if ($this->container) { | ||
if ($this->container && (!Configuration::isBooted() || !FoundryExtension::isEnabled())) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@HypeMC, just for you to know:
now we're deprecating the usage of ResetDatabase
trait in favor of an attribute + usage of the PHPUnit extension, I had errors ServiceNotFoundException: The "kernel" service is synthetic, it needs to be set at boot time before it can be used.
in the database reset testsuite.
Because this currently needs to work with and without the ResetDatabase
trait, the only solution I found was to check if the extension is enabled.
Don't hesitate if you have another idea. Anyway, this ugly stuff will be removed in Foundry 3
f48fbd2
to
a8279d8
Compare
bbeb282
to
874ce5a
Compare
Uh oh!
There was an error while loading. Please reload this page.